You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR keeps kilo.ai/docs in sync with features merged to Kilo-Org/cloud and Kilo-Org/kilocode. Every change below links to the merged PR it documents.
Derivation: Derived from the repository layout. A product surface is a package under packages/ that ships a distinct client, plugin, backend, or hosted service: cli = packages/opencode/ + packages/tui/ + packages/server/ + packages/sdk/ + packages/plugin/; vscode = packages/kilo-vscode/ + packages/kilo-web-ui/ + packages/kilo-ui/; jetbrains = packages/kilo-jetbrains/; gateway = packages/kilo-gateway/; web = packages/kilo-console/ + packages/kilo-indexing/ + packages/kilo-memory/ + packages/kilo-sandbox/. Docs route from the IA tree packages/kilo-docs/pages/ plus docs/jetbrains-vscode-settings-parity.md: each surface lists the pages sections that document it, and the per-platform pages under packages/kilo-docs/pages/code-with-ai/platforms/ map to the matching extension surface (the vscode/ directory to vscode, jetbrains.md to jetbrains). A doc path belongs to the surface with the longest matching prefix; a path that matches none of those prefixes falls to other (the explicit other prefixes are listed under other.docs). The cloud surfaces are derived the same way from the Kilo-Org/cloud layout: cloud-mobile = apps/mobile/, cloud-web = apps/web/, cloud-extension = apps/extension/, and cloud-agent = the cloud-agent packages under packages/ (packages/cloud-agent-sdk/ + packages/cloud-agent-profile/). A cloud source names its repository while a bare string still means this repository. The pages under packages/kilo-docs/pages/collaborate/ document the cloud web app (app.kilo.ai: teams dashboard, billing, SSO, adoption dashboard), so they route to cloud-web. No page under packages/kilo-docs/pages/ documents the browser side-panel extension yet, so cloud-extension lists no docs prefix.
Paths that fall to other: packages/kilo-docs/pages/community/, packages/kilo-docs/pages/kiloclaw/, packages/kilo-docs/pages/contributing/, packages/kilo-docs/LEARNINGS.md, docs/
Reviewers are ranked from Kilo-Org/cloud; the workflow needs a token with contents: read on that repository (repository secret CROSS_REPO_ACCESS_TOKEN, exposed to the upsert step as CLOUD_REPO_TOKEN).
How the two were computed: Reviewers for cloud-agent are ranked from Kilo-Org/cloud git history over packages/cloud-agent-sdk/, packages/cloud-agent-profile/ (a commit 180 days old counts half as much, half-life 180 days). Bots (author type "Bot" or a login matching /[bot]$/i) and people without admin, write, or maintain permission are excluded.
Reply/edit/delete comments, line comments, review submission, suggestion preview/apply, and reactions are already documented under Agent Manager inline review comments and reviews. Verified the behavior is present in current sources (review-actions, suggestion-actions, mutate-comment, pr-patch); no documentation gap found.
The PR removed the experimental multi-project opt-in, but the current tree still gates it behind kilo-code.new.experimental.multiProject (package.json default false; vscode-host/KiloProvider/wiring read the flag) and the multi-project docs page still describes the experimental opt-in. Change not present in current source, so documenting default-on behavior would be inaccurate.
The merged diff adds the GPT-6 Astra Flex model definition with status: 'disabled' and asserts findKiloExclusiveModel(...) returns null, so the model and its flex service tier are not user-visible yet. No user-facing behavior to document.
The opt-in shared agent board (now Kilo Swarm) and its experimental.shared_agent_board setting, board_post/board_read tools, and permissions are already documented in the current tree (settings, Agent Manager, and tools pages); no new user-facing behavior to add.
The Kilo Swarm rename and usage guidance were included in the merged PR and are already present in the current docs (settings Experimental list and Kilo Swarm section); the feature, config key, and tool names match the current tree.
The /update-from-base documentation was included in the merged PR and is already present in packages/kilo-docs/pages/automate/agent-manager.md; the command and behavior match the current source (agent-manager base-update).
Already documented: pages/automate/agent-manager.md (PR Status Badges) already describes the unresolved review-thread count on worktree badges and that the badge, hover-card link, and count open the PR panel at its comments section. Verified the behavior is present in the current tree (webview-ui/agent-manager/WorktreeItem.tsx).
Auto Free routes from a curated server-side pool; the docs describe that pool as dynamic and do not enumerate its members, so no doc change is warranted.
Already documented in packages/kilo-docs/pages/automate/agent-manager.md: local mode can target an existing managed worktree via worktreeID returned by action=list.
Already documented in pages/getting-started/settings/keep-awake.md: default-off Keep Awake across macOS/Linux/Windows, the Agent Manager coffee icon, Command Palette Toggle Keep Awake (kilo-code.new.toggleCaffeination), /caffeinate and aliases, inhibitor only while a session is busy or retrying, release on idle, one-time confirmation stored in extension global state, and platform mechanisms. Verified command id and registration in packages/kilo-vscode/package.json and src/extension.ts. Nothing new from the merged diff needs user-facing docs.
Already documented in pages/automate/agent-manager.md: review threads and conversation comments support the GitHub reaction set (click a pill to toggle or use the picker), and the inline diff/Changes review cards are stated to support the same reaction action as the PR panel. Verified the behavior is present in the current tree (PRStatusPoller reactionGroups with reactors/viewerHasReacted, pr-status-bridge, DiffViewerProvider). No documentation gap.
Auto Free routes from a curated server-side pool. The docs describe that pool as dynamic and do not enumerate its members (pages/getting-started/using-kilo-for-free.md: 'rotates through available free models', 'set of free models is constantly changing'), so changing pool membership (dropping MiniMax, adding an NVIDIA model, reweighting StepFun) requires no doc change. Matches the earlier decision for the related cloud PR 5932.
Already documented in pages/automate/agent-manager.md under Kilo Swarm: Viewing the board (Board icon in the session header, sender/recipient avatars and transcripts, Refresh, cursor-based older-history loading, owner/project scoping) and Resetting the board (clears visible messages, does not stop agents or clear conversations, revision conflict requires refresh). Verified the feature is present in the current tree (kilo-provider/session-board.ts, webview-ui/.../SwarmBoard.tsx, board reset migration). No gap.
Already documented in pages/code-with-ai/agents/goals.md: /goal composer and inline forms, pause/resume/restart/clear controls, Active/Paused/Blocked/Complete statuses, model-reported completion via goal_report, automatic pauses and blocked-on-rejection, clarification disabled during active goals, attachments/drafts, the reserved 'goal' name, and kilo.goal session metadata. Verified the goal domain is present in the current tree (packages/opencode/src/kilocode/session/goal/). No gap.
Already documented: pages/getting-started/settings/notifications.md covers the sound, OS, and VS Code notification settings (all default false), the events and suppression rules, the channel matrix, native support per platform, and the Show/Test actions. Verified the keys and defaults in the current tree (packages/kilo-vscode/package.json kilo-code.new.attention.*) and the delivery logic in src/services/attention/service.ts. No documentation gap.
Connection management is default-off behind GITHUB_CONNECTION_MANAGEMENT_ENABLED (unset or any value other than exact 'true' keeps it disabled) per the PR body and ENVIRONMENT.md diff, so the reconnect/disconnect flow is not user-visible yet.
Already documented: pages/automate/agent-manager.md Conversation section describes the PR description, comments/reviews, grouped consecutive commits, and merged/closed/reopened/force-push lifecycle events in one timeline, plus the Show earlier activity link. Verified the feature is present in the current tree (packages/kilo-vscode/src/agent-manager/pr/timeline.ts). The PR only added the generated visual-regression baseline under kilo-docs; referencing it would require editing the visual-regression DOCS map outside kilo-docs, which this run must not touch.
Auto Free routes from a curated server-side pool; the docs describe that pool as dynamic and do not enumerate its members (pages/code-with-ai/agents/auto-model.md, pages/gateway/models-and-providers.md), so adding nex-agi/nex-n2.5-pro:free and reweighting the pool requires no doc change. Matches the earlier decisions for cloud PRs 5932 and 5947.
Promotional per-model Gemini 3.8 Flash pricing is not documented per model; docs reference the pricing page and the live /api/gateway/models endpoint, so a time-limited discount does not belong in the docs.
Completes the internal autoRouting.models catalog metadata for the Frontier and Small tiers. The docs already describe both tiers and their resolved models and state that underlying mappings are updated server-side (pages/gateway/models-and-providers.md, pages/code-with-ai/agents/auto-model.md), so there is no user-facing behavior change to document. Consistent with prior skips of Auto routing model changes (cloud PRs 5932, 5947, 5995).
Changes internal model aliases, recommendation ordering, and the primary default model used by Auto Balanced and Auto Efficient routing fallbacks. Recommendation lists are intentionally not documented (pages/code-with-ai/agents/model-selection.md defers to a live leaderboard) and the gateway reference describes Auto routing mappings as server-side and changeable without releases (pages/gateway/models-and-providers.md). Cloud source is not in this checkout and the PR diff excerpt is truncated, so the affected fallback path cannot be updated with confidence. Consistent with prior skips of Auto routing model changes (cloud PRs 5932, 5947, 5995).
Documentation was already updated inside the PR: goals.md now says a new message is not an automatic pause and only shell commands pause it. Current source (goal/runner.ts consumeSuperseded loop, prompt-queue.ts superseded markers) matches the docs, so no further change is needed.
Organization sandbox selection is gated behind the SANDBOX_SELECTION_IDS allowlist (empty by default and requires enrollment) plus worktree-creation rollout flags, so it is not user-visible yet.
The docs do not enumerate Auto Free candidate models; using-kilo-for-free.md already states that available free models change over time, so the internal routing/weight change has no user-facing doc to update.
Internal fix for a bug that already contradicted documented behavior. The docs already state that active local CLI sessions appear in the Cloud Agents dashboard and mobile app; this PR makes locally started sessions actually appear. No user-facing capability or option changed.
The user-visible behavior is already documented: automate/agent-manager.md covers board sender/recipient avatars and the direct-recipient execution-state and aggregate availability warnings exposed by board_post, matching the current board.ts and store.ts implementations. The remaining changes are tool-card layout and i18n.
The Auto Free pool is documented as a server-side dynamically resolved set, and individual pool models are intentionally not enumerated in the docs, so adding one member model needs no doc change.
Removes stepfun/step-3.7-flash:free only from the Auto Free routing pool while keeping it public in the catalog. The docs free-model list is a catalog entry (gateway/models-and-providers.md:63) and Auto Free routing is already documented as server-side/dynamic, so no user-facing docs change.
Marks thinkingmachines/inkling:free as unavailable in the OpenRouter catalog. The model is not mentioned anywhere in the docs, and free-model availability is already documented as changing over time (auto-model.md, using-kilo-for-free.md), so no docs update is needed.
(bot) Generated by the docs-sync workflow. Humans review and merge; while this PR stays open, the next daily run appends new changes here. Branch: docs/auto-sync-2026-09-14.
Docs-only auto-sync adding CLI --prompt-stdin usage, worktree/chat model, workspace folders, and changed-file viewing to the Cloud Agent page. The --prompt-stdin documentation matches the CLI implementation (packages/opencode/src/kilocode/cli/cmd/cloud-stdin.ts:23, wired into both cloud start and cloud send), heading levels are sequential, and no markdown/memory-leak concerns apply to this change. Other cloud web UI descriptions originate from the cloud repo and are not verifiable in this checkout; no defects were identified on the changed lines.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated docs sync — 2026-09-14
This PR keeps kilo.ai/docs in sync with features merged to Kilo-Org/cloud and Kilo-Org/kilocode. Every change below links to the merged PR it documents.
2026-08-31T00:00:00.000Z→2026-09-09T07:34:02.999ZSurface:
cloud-agentother(the explicit other prefixes are listed under other.docs). The cloud surfaces are derived the same way from the Kilo-Org/cloud layout: cloud-mobile = apps/mobile/, cloud-web = apps/web/, cloud-extension = apps/extension/, and cloud-agent = the cloud-agent packages under packages/ (packages/cloud-agent-sdk/ + packages/cloud-agent-profile/). A cloud source names its repository while a bare string still means this repository. The pages under packages/kilo-docs/pages/collaborate/ document the cloud web app (app.kilo.ai: teams dashboard, billing, SSO, adoption dashboard), so they route to cloud-web. No page under packages/kilo-docs/pages/ documents the browser side-panel extension yet, so cloud-extension lists no docs prefix..github/docs-sync/surfaces.jsoncli,vscode,jetbrains,gateway,web,cloud-mobile,cloud-web,cloud-extension,cloud-agent,otherpackages/cloud-agent-sdk/(Kilo-Org/cloud),packages/cloud-agent-profile/(Kilo-Org/cloud)packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.mdother:packages/kilo-docs/pages/community/,packages/kilo-docs/pages/kiloclaw/,packages/kilo-docs/pages/contributing/,packages/kilo-docs/LEARNINGS.md,docs/Kilo-Org/cloud; the workflow needs a token withcontents: readon that repository (repository secretCROSS_REPO_ACCESS_TOKEN, exposed to the upsert step asCLOUD_REPO_TOKEN).cloud-agentare ranked fromKilo-Org/cloudgit history overpackages/cloud-agent-sdk/,packages/cloud-agent-profile/(a commit 180 days old counts half as much, half-life 180 days). Bots (author type "Bot" or a login matching /[bot]$/i) and people without admin, write, or maintain permission are excluded.Changes
Pending — will retry
Considered, no docs change needed
(bot) Generated by the docs-sync workflow. Humans review and merge; while this PR stays open, the next daily run appends new changes here. Branch:
docs/auto-sync-2026-09-14.